System and method for generating communication subscriber description information

ABSTRACT

A system for generating communication subscriber description information includes an information labeling unit adapted to label original information of a specific communication subscriber, and a subscriber information generating unit adapted to generate communication subscriber description information according to communication records. A method for generating communication subscriber description information applies Ontology in the communication field, so as to obtain subscriber demand information for generating communication subscriber description information by analyzing actual communication records of the subscriber. Moreover, the generated communication subscriber description information truly reflects characteristics and requirements of the communication subscriber, thus ensuring the accuracy of the generated communication subscriber description information. The present invention is applicable to communication behaviors such as voice communication, data communication, and short messages of a subscriber.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Patent ApplicationNo. PCT/CN2007/000790, filed Mar. 12, 2007, which claims priority toChinese Patent Application No. 200610104256.2, filed Aug. 7, 2006, bothof which are hereby incorporated by reference in their entirety.

FIELD OF THE TECHNOLOGY

The present invention relates to a communication information collectiontechnology, and more particularly to a system and a method forgenerating communication subscriber description information.

BACKGROUND

With the development of modern communication technology, people cancommunicate with each other in many diversified ways, from fixed-linephones and mobile phones for voice communication, to Emails and mobileEmails mainly for text communication, to instant messages (IMs) whichcombine voice, text, and even image communication; and from the BBSForums of Web1.0 to the multimedia-filled Blogs of Web 2.0. Meanwhile,various communication modes are becoming gradually integrated. Forexample, a subscriber can now conduct voice communication, Email sendingand receiving, and IM communication all through one mobile terminal. Inaddition, one can even achieve information communication through variousdata services like mobile Blogs, picture Blogs, and Podcasts.

Relevant data show that, under current conditions, on average 170million call records are produced each month in a district with 700,000GSM subscribers. This interpersonal communication builds a huge socialrelationship network, and at the same time, such communication containsabundant communication subscriber description information reflecting thecharacteristics and requirements of the subscribers. For example, when asubscriber regularly dials the service hotline of a securities company,it can be deduced that the subscriber is possibly a shareholder. Thusproducts about investment and financing might well interest thesubscriber. Therefore, certain attributes of the securities company canbe transferred to the subscriber. In today's user-centered society, oneextremely significant issue is how to obtain communication subscriberdescription information.

In another aspect, Ontology has become a hot-point in research at homeand abroad, and its applications appear in various fields. The study ofOntology is focused on knowledge engineering, ontology engineering,information organization and retrieval, and semantic Web. Variousontology languages and ontology creation tools are being graduallydeveloped and utilized. For example, Protégé is a free and open-sourceontology editor and knowledge management platform developed by MedicalInformation Center of Stanford University School of Medicine. Jena is adevelopment kit from the HP Company for the application of semanticnetwork-oriented ontology parsing and rule reasoning, and its content iscomprehensive. As for ontology languages, Web Ontology Language (OWL)has become a recommended standard for World Wide Web Consortium (W3C).It has become a trend to use Ontology in traditional and emergingindustries.

Ontology is applied in the communication world to describe the attributecharacteristics of each communication subject using ontology languages,thereby capturing the transferring of the attribute characteristics in asocial network. This is significant for obtaining the descriptioninformation of subscribers functioning as main communication subjects.

Besides launching a 1 G mailbox to serve the subscribers, the Gmailservice of Google company further built a subscriber relationshipnetwork through recommendations among net-friends, so as to obtaininformation such as social relationships of the subscribers, therebygenerating some communication subscriber description information. In theearly stage, new subscribers of Gmail could only obtain mailbox accountsthrough the invitations of old subscribers. Thereby, a social network isbuilt by social relationship attributes of the subscribers collectedthrough invitation authorities among net-friends. However, in practice,an old subscriber of Gmail may not only invite his friends. When Gmailfirst appeared, many Gmail owners sold their invitation authority inpublic on the Internet, and after Gmail became popular, it became easyto obtain Gmail invitations through the Internet. As a result, thesocial relationship information built on the basis of invitationauthorities is not accurate. In other words, the generated communicationsubscriber description information is inaccurate.

Another method for generating communication subscriber descriptioninformation is shown below. The Email sending and receiving records of asubscriber are analyzed by a server to obtain the information of whichtype of Email addresses the subscriber contacts, and thus the subscriberdescription information can be generated according to the Emailaddresses information. However, Email providers can only build a simplecontact network by analyzing the Email sending and receiving records.Such inadequate communication subscriber description information may nottruly reflect the characteristics and requirements of the subscriber,and thus is inaccurate.

SUMMARY

Accordingly, an embodiment of the present invention provides a systemfor generating communication subscriber description information. Thesystem can automatically generate communication subscriber descriptioninformation, so as to ensure the accuracy of the generated communicationsubscriber description information.

An embodiment of the present invention also provides a method forgenerating communication subscriber description information. The methodcan automatically generate communication subscriber descriptioninformation, so as to ensure the accuracy of the generated communicationsubscriber description information.

As embodied and broadly described herein, the present invention furtherprovides the following technical scheme.

A system for generating communication subscriber description informationis provided, including (1) an information labeling unit adapted to labeloriginal information of a specific communication subscriber, and (2) asubscriber information generating unit adapted to generate communicationsubscriber description information.

The information labeling unit includes a labeling module, an originalresource database, an application template ontology library, and aspecific subscriber labeling library.

The original resource database is adapted to record the originalinformation of a subscriber to be labeled.

The application template ontology library is adapted to build and storean application template describing a class and class attributes of theapplication for different applications. The class and class attributescome from a public or self-defined ontology in an industrial applicationfield.

The labeling module is adapted to obtain the original information of asubscriber to be labeled from the original resource database, call anapplication template corresponding to the class from the applicationtemplate ontology library according to the class of the originalinformation, and fill information corresponding to the applicationtemplate in the original information into the application template so asto label the original information, and store the labeled originalinformation in the specific subscriber labeling library.

The subscriber information generating unit includes a subscriberinformation generating module, a subscriber information base, a strategypool, and a strategy setting module.

The subscriber information generating module is adapted to obtaincommunication and record information externally, query the specificsubscriber labeling library, and according to the informationtransferring strategy of an unspecific subscriber in the strategy pool,add a qualified contact party ID information into the communicationsubscriber description information of a communication subject and storethe communication subscriber description information in the subscriberinformation base; or according to the information transferring strategyof a specific subscriber in the strategy pool, add a qualified contactparty ID information and the corresponding subscriber labeledinformation of the contact party ID information stored in the specificsubscriber labeling library into the communication subscriberdescription information of a communication subject, and store thecommunication subscriber description information in the subscriberinformation base.

The strategy setting module is adapted to set and store varioussubscriber information transferring strategies into the strategy pool.

The strategy pool is adapted to store and provide various subscriberinformation transferring strategies for the subscriber informationgenerating module.

The subscriber information base is adapted to store subscriberdescription information files of communication subjects.

The system further includes a preprocessing unit adapted to preprocesscommunication records, and the preprocessing unit includes a recordpreprocessing module and a new record library.

The record preprocessing module is adapted to extract a preset targetfield from fields of the externally obtained communication recordinformation, generate an additional field after processing thecommunication records according to a preset requirement, and store a newrecord composed of the target field and the additional field.

The new record library is adapted to store target fields and additionalfields to compose new communication records for the subscriberinformation generating module.

The information labeling unit further includes a self-service moduleadapted to provide a subscriber interface, so as to update labelingresults in the specific subscriber labeling library through the labelingmodule by the self-service module.

The self-service module is an operating platform, or a client in aclient/server (C/S) architecture, or a client in a browser/server (B/S)architecture.

The labeling module further includes a mapping table between fields inthe application template and their corresponding ambiguous fields.

The labeling module further includes a split function for analyzing theambiguous fields corresponding to the fields in the application templateso as to extract a key field.

The application template includes an application template name andapplication template parameters describing the class attributes of theclass indicated by the application template name. The applicationtemplate name is identical to the name of the class.

The application template further includes association relationshipsbetween different classes.

A method for generating communication subscriber description informationincludes presetting a subscriber information transferring strategy fordetermining whether or not to add contact party information into thecommunication subscriber description information of a communicationsubject. The method further includes (1) obtaining the communicationrecord information, and determining whether the contact party IDinformation in the communication record information exists in thegenerated subscriber labeled information; (2) if the contact partyidentification (ID) information in the communication record informationdose not exist in generated subscriber labeled information, according toan information transferring strategy of an unspecific subscriber in thepreset subscriber information transferring strategy, recording thequalified contact party ID information in the communication recordinformation into the communication subscriber description information ofthe communication subject, and ending the process; and (3) if thecontact party identification (ID) information in the communicationrecord information exists in generated subscriber labeled information,according to the information transferring strategy of a specificsubscriber in the preset subscriber information transferring strategy,recording the qualified contact party ID information in thecommunication record information and the subscriber labeled informationcorresponding to the contact party ID information into the communicationsubscriber description information of the communication subject.

An application template describing a class and class attributes of theapplication is respectively preset for different applications, and themethod for generating the subscriber labeled information includes (1)extracting an original resource data record, and obtaining the classname of the class of the original resource data record; (2) calling anapplication template corresponding to the class name according to theobtained class name, and recording a corresponding field value in therecord into the application template according to the fields containedin the called application template; and (3) storing the applicationtemplate after recording.

If parts of the fields in the application template do not exist in theoriginal resource data record, the method for recording thecorresponding field value in the original resource data record into theapplication template is setting the field value in the applicationtemplate as null.

If parts of the fields in the application template do not exist in theoriginal resource data record, the method for recording thecorresponding field value in the original resource data record into theapplication template includes (1) presetting a mapping table between thefields in the application template and their corresponding ambiguousfields; and (2) querying the mapping table to determine whether theambiguous field of the field in the application template exists in theoriginal resource data record, and if the ambiguous field of the fieldin the application template exists in the original resource data record,analyzing and extracting a key field from the ambiguous field, andrecording the key field in the corresponding field of the applicationtemplate; otherwise, setting the value of the field in the applicationtemplate as null.

The method for analyzing and extracting a key field is split analysis.

If the field described in the conditions of the subscriber informationtransferring strategy does not exist in the obtained communicationrecord information, before determining whether the contact party IDinformation in the communication record information exist in thegenerated subscriber labeled information, the method further includesextracting a preset target field from the fields of the obtainedcommunication record and generating an additional field after processingthe communication record information according to a preset requirement,so as to form and restore new communication record information.

If the contact party ID information in the communication recordinformation exists in the generated subscriber labeled information, amethod for recording the subscriber labeled information includes (1)traversing preset preferential attributes in the subscriber descriptioninformation of a communication subject subscriber, determining whetherthe class of the subscriber labeled information exists in thepreferential attributes, and if the class of the subscriber labeledinformation does not exist in the preferential attributes, adding theclass of the subscriber labeled information and transferable parameterstherein into the preferential attributes of the communication subjectsubscriber; and further determining whether the transferable parametersin the subscriber labeled information exist in the preferentialattributes, if the transferable parameters in the subscriber labeledinformation exist in the preferential attributes, the process ends;otherwise, the transferable parameters in the subscriber labeledinformation are added into the preferential attributes.

The method further includes: in the communication subscriber descriptioninformation, building contact frequency or intimacy between thecommunication subject and an unspecific subscriber or a specificsubscriber according to a preset composite operation relationship of adesignated field.

The application template is created on the basis of an OntologyLanguage.

The application template includes an application template name andapplication template parameters describing related class attributes ofthe class indicated by the application template name.

Seen from the above technical scheme, the present invention obtainssubscriber demand information for generating communication subscriberdescription information through applying Ontology in the communicationfield and analyzing actual communication records of the subscriber.Moreover, the generated communication subscriber description informationtruly reflects characteristics and requirements of communicationsubscribers, thus ensuring the accuracy of the generated communicationsubscriber description information.

The present invention is applicable to communication behaviors such asvoice communication, data communication, and short messages of asubscriber.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram showing the configuration of a system forgenerating communication subscriber description information according toan embodiment of the present invention;

FIG. 2 is a flow chart of a method for generating communicationsubscriber description information according to an embodiment of thepresent invention;

FIG. 3 is a flow chart illustrating information labeling according to anembodiment of the present invention;

FIG. 4 is a flow chart of a method for recording a subscriberapplication template according to an embodiment of the presentinvention; and

FIG. 5 is a flow chart of an embodiment of the present invention.

DETAILED DESCRIPTION

Embodiments of the present invention include: presetting a subscriberinformation transferring strategy, obtaining communication recordinformation, and determining whether a contact party identification (ID)information in the communication record information exists in generatedsubscriber labeled information. If the contact party identification (ID)information in the communication record information does not exist ingenerated subscriber labeled information, the qualified contact party IDinformation in the communication record information is recorded,according to an information transferring strategy of an unspecificsubscriber in the preset subscriber information transferring strategy,into the communication subscriber description information of acommunication subject. If the contact party identification (ID)information in the communication record information exists in generatedsubscriber labeled information, the qualified contact party IDinformation in the communication record information and the subscriberlabeled information corresponding to the contact party ID information isrecorded, according to an information transferring strategy of aspecific subscriber in the preset subscriber information transferringstrategy, into the communication subscriber description information ofthe communication subject.

In order to make the objectives, technical scheme, and advantages of thepresent invention comprehensible, exemplary embodiments accompanied withfigures are described in detail below.

The present invention is applicable to communication behaviors such asvoice communication, data communication, and short messages of asubscriber. Voice communication is taken as an example below fordescribing the whole realizing process.

FIG. 1 is a schematic diagram showing the configuration of a system forgenerating communication subscriber description information according toan embodiment of the present invention. The embodiment of the system ofthe present invention includes an information labeling unit 10 adaptedto label original information of a specific communication subscriber,and a subscriber information generating unit 12 adapted to generatecommunication subscriber description information according tocommunication records. The communication subscriber hereinafter isreferred to as subscriber for short. The composition of the units andconnections there-between will be illustrated in detail below.

Firstly, the information labeling unit 10 includes a labeling module100, an original resource database 101, an application template ontologylibrary 102, and a specific subscriber labeling library 103.

The original resource database 101 is adapted to record the originalinformation of a subscriber to be labeled. The original informationincludes ID information and attributes describing the subscriber. Forexample, original data of an enterprise registered in the yellow pages;such as the class of the enterprise, enterprise name, telephone number,service introduction, district, address, fax, postcode, address, andEmail. The class records leaf nodes of the trade catalog of the company,the telephone number of the company functions as the ID information, andthe rest of the parameters serve as the attribute descriptioninformation. It should be noted that, the specific subscriber hereinrefers to a labeled communication subscriber.

For example, in an IM communication network, IM numbers are furtherclassified as enterprise subscribers and ordinary subscribers, and thusthe original resource database refers to information records of an IMenterprise subscriber. The same processing mode can be applied toservices with numbers like Email.

The application template ontology library 102 is adapted to build andstore an application template describing a class and class attributes ofan application for different applications. The class and classattributes come from a public or self-defined ontology in an industrialapplication field. In particular, directing to different applications,large classes, sub-classes thereof, ontology of class attributes arebuilt according to the classification manner of the original resourcedata, and relationships between the classes and associations between theclass attributes are defined. Meanwhile, the relationship between theclasses and class attributes is defined to point out class attributesfor describing each class and sub-classes thereof, and an applicationtemplate of the class is deduced by the relationship. It should be notedthat, if the original resource data has not been classified, it can bedone manually, and meanwhile ontology of the class library is created.Herein, the application template is created on the basis of an OntologyLanguage. The creation method adopts a current technology, and can beaccomplished by many current ontology creation tools. For example,Protege platform mentioned in the background of the invention, whichwill not be described in detail herein again.

An application template includes two parts: an application template namefor identifying the class of the application template, and applicationtemplate parameters describing the class attributes of the classindicated by the application template name. The application templatename is identical to the name of the class. When the applicationtemplate parameters are set, each application template parameter iscorresponding to a type tag. The application template parameters can beclassified into transferable parameters and non-transferable parameters,or even more specified types. When a parameter is set as a transferableparameter, the parameter can be transferred to the subscriber as asubscriber description information record.

Due to different characteristics, each industry needs specificapplication template parameters to describe its attributes. For example,in the auto industry, attributes of brands are employed for identifyingauto models run or manufactured by a company. While in the restaurantindustry, the attributes of brands may not exist, parameters describingthe taste and decoration style are more often used. Therefore, differentapplication templates can be set directing to leaf nodes of theclassified catalog of different industries. Each application templatehas a uniquely allocated template name and application templateparameter description directing to the industry having the leaf node.

An application template of the auto sales class is taken as an examplebelow, for illustrating possible application template parameters of aspecific subscriber in the auto sales. Referring to Table 1:

TABLE 1 Application template name: Auto Sales Contained applicationtemplate parameters Group 1: Basic Attributes (Inherent Attributes)Company name: Telephone number: Address: City: Postcode: Website: Group2: Extended Attributes (Service Attributes) Brands: such as BMW,CITROEN, FVW, etc Services: such as auto sales, auto insurance, automaintenance, etc

Table 1 describes possible content in an application template of autosales in words. The parameters in practice implementation are setaccording to actual circumstances, which include, but is not limited to,the content of Table 1.

In practice, Ontology Language, for example, Web Ontology Language (OWL)can be used to describe and record an application template, and thedetail of such description is well known in the art. The presentinvention emphasizes the creation of specific application templates fordifferent applications (classes).

The application template not only labels various application templateparameters for classes, but also builds association relationshipsbetween different classes. For example, the association relationshipbetween the auto sales in the auto class and the petrol sales in thechemical industry class can be built, which means the subscriber of autosales may also be the subscriber of petrol sales at the same time. Thistransitive relationship may well contribute to the collection ofsubscriber attributes.

The labeling module 100 is a logic processing module of the informationlabeling unit 10, adapted to label the original information of asubscriber. The original information of a subscriber to be labeled isobtained from the original resource database 101. According to the classof the original information, an application template corresponding tothe class is invoked from the application template ontology library 102.An application template name and parameter values of the applicationtemplate parameter items corresponding to the application template inthe original information are filled into the application template, so asto obtain the specific subscriber information, and store the obtainedspecific subscriber information in the specific subscriber labelinglibrary 103.

When labeling the attributes of a specific subscriber, differentapplication templates can be invoked to label the specific subscriberinformation directing to subscribers in different types of industries.

The specific subscriber labeling library 103 is adapted to store thelabeled specific subscriber information.

The labeled specific subscriber information includes, but is not limitedto, ID information of a specific subscriber such as telephone number,application template name of the specific subscriber, and descriptioninformation of the specific subscriber. The description information ofthe specific subscriber includes, but is not limited to, basicattributes and extended attributes. The specific subscriber informationis stored in the specific subscriber labeling library 103 in a feasiblestorage manner. Table 2 shows an embodiment of the stored specificsubscriber information:

TABLE 2 <Specific Subscriber 1> <ID Number></ID Number> <TemplateName>Auto Sales</Template Name> <Attribute Parameters>   <Group 1: BasicAttributes>     <Enterprise Name></Enterprise Name>    <District></District>     <Address></Address>    <Postcode></Postcode>     <Website></Website>   </Group 1: BasicAttributes>   <Group 2: Extended Attributes>     <Brand></Brand>    <Service item></Service item>   </Group 2: Extended Attributes></Attribute Parameters> </Specific Subscriber 1>

The information labeling unit 10 further includes a self-service module104 adapted to provide a subscriber-oriented interface, so as tofacilitate the subscriber to update labeling results in the specificsubscriber labeling library 103 through the labeling module 100 by usingthe self-service module 104. If the subscriber is a system manager, theself-service module 104 serves as an operating platform like systeminterface. If the subscriber is a labeled subscriber, a client/server(C/S) architecture is adopted, in which the self-service module 104serves as a client, and the labeling module 100 and the specificsubscriber labeling library 103 serve as a server. After logging on theserver through the client, the labeled subscriber can modify the labeledself-information through operations such as registration, logon, orinformation update at the client. Herein, as the C/S structure is acommonly-used architecture at present, and belongs to a technology knownto those skilled in the art, so the details will not be described hereinagain. Further, the self-service module 104 may also be implemented as aclient in a browser/server (B/S) architecture.

Secondly, the subscriber information generating unit 12 includes asubscriber information generating module 120, a subscriber informationbase 121, a strategy pool 122, and a strategy setting module 123.

The subscriber information generating module 120, a core module in thesystem of the present invention, is adapted to determine whether or notand how to generate the communication subscriber description informationaccording to a subscriber information transferring strategy queried andinvoked from the strategy pool 122, and further store the generatedcommunication subscriber description information into the subscriberinformation base.

The subscriber information generating module 120 obtains communicationrecord information externally, and queries the specific subscriberlabeling library 103 to determine whether communication objects in thecommunication records, i.e., ID field values of the contact parties, arestored in the specific subscriber labeling library 103. If communicationobjects are not stored in the specific subscriber labeling library 103,qualified contact party ID information is added, according to aninformation transferring strategy of an unspecific subscriber in thesubscriber information transferring strategy, into the communicationsubscriber description information of a communication subject, and thecommunication subscriber description information is further stored inthe subscriber information base 121. If communication objects are storedin the specific subscriber labeling library 103, qualified contact partyID information and the corresponding subscriber labeled information ofthe contact party ID information stored in the specific subscriberlabeling library 103 are added, according to an information transferringstrategy of a specific subscriber in the subscriber informationtransferring strategy, into the communication subscriber descriptioninformation of a communication subject, and the communication subscriberdescription information is further stored in the subscriber informationbase 121.

If the communication object is a specific subscriber in the specificsubscriber labeling library, the subscriber labeled information is addedinto the subscriber information base 121, that is, a preferentialattribute is recorded in the communication subscriber descriptioninformation of the communication subject. If the preferential attributealready exists, the preferential attribute information is adjusted, forexample, to add in new transferable parameters or alter thecorresponding weights of the parameters. If the preferential attributealready does not exist; the preferential attribute information is added.

Herein, the communication subject refers to a home subscriber of acommunication record, for example, a calling party number subscriber ina calling party bill record, and thus the communication subject isidentified by the subscriber number fields in the bill record.

The strategy setting module 123 is a system-manager-oriented managementinterface, for setting various subscriber information transferringstrategies. In practice, different classes have specificcharacteristics, so different subscriber information transferringstrategies should be set. The already set subscriber informationtransferring strategies are stored in the strategy pool 122.

The subscriber information transferring strategy includes conditions forbuilding attributes of an unspecific subscriber and conditions forbuilding attributes of a specific subscriber. Here, the unspecificsubscriber, relative to the specific subscriber, refers to a subscribernot existing in the specific subscriber labeling library 103. Accordingto the conditions for building attributes of an unspecific subscriber,it is determined whether or not to add the unspecific subscriber intothe communication subscriber description information of a communicationsubject. According to the conditions for building attributes of aspecific subscriber, it is determined whether or not to add the specificsubscriber into the communication subscriber description information ofa communication subject.

The subscriber information transferring strategy is a descriptioncombination of field value restrictions, and the fields here come fromthe communication records. A subscriber information transferringstrategy can be expressed in Formula (1) as follows:

I={Q ₁ ∩Q ₂ ∩ . . . ∩Q}(n>=1)  (1)

In Formula (1), I represents the content of a subscriber informationtransferring strategy, Q represents different field values, i.e.,restrictions, and ∩ represents an AND relationship between the previousand succeeding restrictions. As shown in Formula (1), it is consideredqualified to meet the subscriber information transferring strategy onlywhen all the restrictions Q₁-Q_(n) are satisfied. It should be notedthat, Formula (1) is only one way of expressing the subscriberinformation transferring strategy, and the relationship between theprevious and succeeding restrictions can also be OR, or partially ANDwhile partially OR, which will not be illustrated in detail hereinagain.

Table 3 shows the content and definitions of subscriber informationtransferring strategies for specific subscribers with applicationtemplate names as auto sales class and auto maintenance class:

TABLE 3 Content of subscriber information Application transferringtemplate name strategy Meanings Auto sales I₁ = {(the number Thetransferable information of any of calls >1)} auto sales contact partymaking more than one call will be recorded in the communicationsubscriber description information of a communication subject. Auto I₂ ={(the number Only the transferable information of maintenance of calls >3) ∩ an auto maintenance contact party (total call who makes more thanthree calls and duration > with the total call duration exceeding00:15:00)} 15 minutes will be recorded in the communication subscriberdescription information of a communication subject.

The strategy pool 122 is adapted to store and provide various subscriberinformation transferring strategies for the subscriber informationgenerating module. In the strategy pool 122, one application templatename is corresponding to one subscriber information transferringstrategy. The subscriber information generating module 120 queries andinvokes the corresponding subscriber information transferring strategyin the strategy pool 120 according to the application template name ofthe original resource data.

The subscriber information base 121 is adapted to store the subscriberdescription information file of a communication subject. The subscriberdescription information file includes, but is not limited to,identification IDs, social relationship attributes, and preferentialattributes of the subscriber.

The social relationship attributes record unspecific subscribers,specific subscribers, and contact weight between subscribers who meetthe conditions for building the social relationships. The contact weightis a parameter showing the degree of relationship between thesubscribers, and can be obtained by certain combination operations basedon a specific field, so as to present the contact frequency or intimacybetween the communication subject and unspecific or specificsubscribers. A combination operation is taken here as an example.Assuming that the contact weight is represented by S and the specificfield set by the system is represented by P, Formula (2) is obtained asfollows:

$\begin{matrix}{{S = {{f\left( {P_{1},P_{2},\ldots \;,P_{n}} \right)} = \frac{P_{m}}{\sum\limits_{i = 1}^{n}P_{i}}}},{n>=m>=1}} & (2)\end{matrix}$

The preferential attributes are mainly formed by transferable parametersof different application templates, for describing characteristics ofspecific subscribers in already built social relationships. Aftermeeting the conditions for building social relationships, thecharacteristics are transferred to the communication subject fordescribing the communication subscriber description information of thecommunication subject. Table 4 shows an example of a subscriberinformation record. Subscriber 1 represents a communication subject. Thecommunication subscriber description information of the communicationsubject includes information of an unspecific subscriber 1, anunspecific subscriber 2, a specific subscriber 1, and a specificsubscriber 2. The preferential attributes are formed by transferableparameters of an application template 1 and an application template 2,for describing characteristics of the specific subscriber 1 and thespecific subscriber 2 in already built social relationships.

TABLE 4 <subscriber 1>   <number></number>   < social relationshipattributes>    <unspecific subscriber>     <unspecific subscriber 1>      <number></number>       <contact weight></contact weight>    </unspecific subscriber 1>     <unspecific subscriber 2>      <number></number>       <contact weight></contact weight>    </unspecific subscriber 2>    </unspecific subscriber>    <specificsubscriber>     <specific subscriber 1>       <number></number>      <name></name>       <contact weight></contact weight>    </specific subscriber 1>     <specific subscriber 2>      <number></number>       <name></name>       <contactweight></contact weight>     </specific subscriber 2>    </specificsubscriber>   </ social relationship attributes>   <preferentialattribute>    <application template 1>     <template name>auto sales</template name>     <transferable parameter a></transferable parametera>     <transferable parameter b></transferable parameter b>   </application template 1>    <application template 2>     <templatename>yacht sales</template name>     <transferable parametera></transferable parameter a>     <transferable parameterb></transferable parameter b>    </application template 2>  </preferential attribute> </subscriber 1>

In practice, the information labeling unit 10 and the subscriberinformation generating unit 12 can be two independent servers.

Further, if the communication record information obtained externally bythe subscriber information generating module 120 does not include thefields described in the restrictions of the subscriber informationtransferring strategy, the system of the present invention furtherincludes a preprocessing unit 11 adapted to preprocess the communicationrecords. In particular, a preset target field is extracted from thefields of the original communication record to form a new record, andthe new record is stored. The target field at least includes acommunication subject ID field identifying the owner of thecommunication record, a contact party ID field identifying thecommunication objects, and an additional field generated by processingthe communication record according to preset requirements.

The preprocessing unit 11 mainly includes a record preprocessing module110 and a new record library 111.

The record preprocessing module 110 is adapted to preprocess theexternally obtained communication record information, extract a presettarget field from the fields of the original communication record toform a new record, and store the new record. Meanwhile, the new recordfurther includes an additional field generated by processing thecommunication record according to preset requirements. The newcommunication record composed of the target field and the additionalfield is stored in the new record library 111.

Herein, take the preprocessing of an externally obtained original phonebill as an example for illustration. Table 5 shows an original phonebill record, including subscriber number, serial number, place of thecall, type of the calling/called party, type of the call, counterpart'snumber, date of the call, time of the call, duration of the call, mobilephone charge, and toll call charge. It is assumed that the preset targetfields are subscriber number, serial number, counterpart's number, thenumber of calls, and total call duration. Seen from Table 5, thesubscriber number, serial number, and counterpart's number can bedirectly extracted from the original phone bill record. However, thenumber of calls and total call duration do not exist in the originalphone bill record, and can be obtained by consolidating the same billrecords, i.e., consolidating bill records with the same contact party IDfield values, which refer to bill records with the same counterpart'snumber. Further, the consolidation here actually means summation. Forexample, the total call duration of a counterpart's number A can beobtained by merely adding together the call duration in each recordunder the counterpart's number A in the original phone bill record.

TABLE 5 Original Phone Bill Record Subscriber Ser. Place of Type of TypeCounterpart's Date Time Duration Mobile Toll call number No. the callthe calling/ of the number of the of the of the phone charge called callcall call call charge party

The new record library 111 is adapted to store the preprocessedcommunication records, and the subscriber information generating module120 obtains the required communication records from the new recordlibrary 111. The record fields are target fields preset by the recordpreprocessing module 110. According to the above example, the billrecords preprocessed and stored in the new record library 111 are shownin Table 6:

TABLE 6 Preprocessed communication records Subscriber Ser. Place of Typeof the Number of Total call number No. the call calling/called partycalls duration

In Table 6, the subscriber number field means that the bill recordbelongs to the communication subscriber corresponding to the subscribernumber, number of calls represents the total entries in the same bill,and the total call duration refers to the sum of call durations in thesame bill.

The system for generating communication subscriber descriptioninformation provided by the embodiment of the present invention isdescribed above, and the method for generating communication subscriberdescription information according to the present invention will bedescribed in detail below accompanied by FIG. 1. FIG. 2 is a flow chartof the method for generating communication subscriber descriptioninformation according to an embodiment of the present invention. Themethod can be controlled and implemented by a preset timer, or performedunder the command from a background manager. The method mainly includesthe following blocks.

Block 200: a subscriber information transferring strategy is preset.

The subscriber information transferring strategy includes conditions forbuilding attributes of an unspecific subscriber and conditions forbuilding attributes of a specific subscriber. According to theconditions for building attributes of an unspecific subscriber, it isdetermined whether or not to add the information of an unspecificsubscriber into the communication subscriber description information ofa communication subject; and according to the conditions for buildingattributes of a specific subscriber, it is determined whether or not toadd the information of a specific subscriber into the communicationsubscriber description information of a communication subject. Theinformation transferring strategy has already been illustrated in detailduring the description of the strategy setting module 123, so thedetails will not be given herein again.

Block 201: The communication record information is obtained, and it isdetermined whether the contact party ID information in the communicationrecord information exists in the generated subscriber labeledinformation. If the contact party ID information exists in the generatedsubscriber labeled information, the process proceeds to Step 203; if thecontact party ID information does not exist in the generated subscriberlabeled information, the process proceeds to Block 202.

The communication records can be obtained in various manners, forexample, reading from a database particularly for storing communicationrecords. The actual implementation has nothing to do with the presentinvention, so the details will not be illustrated herein again.

Block 202: According to an information transferring strategy of anunspecific subscriber in the preset subscriber information transferringstrategy, the qualified contact party ID information in thecommunication record information is recorded into the communicationsubscriber description information of a communication subject, and thenthe process is ended.

The contact party ID may be telephone numbers.

Block 203: According to an information transferring strategy of aspecific subscriber in the preset subscriber information transferringstrategy, the qualified contact party ID information in thecommunication record information and the subscriber labeled informationcorresponding to the contact party ID information are recorded into thecommunication subscriber description information of a communicationsubject.

In this block, the subscriber labeled information corresponding to thecontact party ID information may be the transferable informationobtained from the generated subscriber labeled information afterdetermining that the contact party ID information in the communicationrecord information exists in the generated subscriber labeledinformation in Block 201, or the transferable information obtained fromthe generated subscriber labeled information according to the contactparty ID after the qualified conditions are determined in Block 203.

A method for recording the subscriber labeled information includestraversing preset preferential attributes in the subscriber descriptioninformation of a communication subject subscriber, and determiningwhether the class of the subscriber labeled information exists in thepreferential attributes. If the class does not exist in the preferentialattributes, the class of the subscriber labeled information andtransferable parameters therein are added into the preferentialattributes of the communication subject subscriber. If the class existin the preferential attributes, it is further determined whether thetransferable parameters in the subscriber labeled information exist inthe preferential attributes, if the transferable parameters exist in thepreferential attributes, the process ends; if the transferableparameters do not exist in the preferential attributes, the transferableparameters in the subscriber labeled information are added into thepreferential attributes.

In this Block, the method for generating the subscriber labeledinformation is shown in FIG. 3. FIG. 3 is a flow chart illustratinginformation labeling according to an embodiment of the presentinvention. The method includes the following blocks.

Block 300: An original resource data record is extracted, and the classname of the class of the record is obtained.

Herein, an original resource data record is a record in thecommunication record information.

Block 301: According to the obtained class name, an application templatecorresponding to the class name is invoked, and according to fieldscontained in the invoked application template, corresponding fieldvalues in the record are recorded into the application template.

In this block, the application template is preset.

If parts of the fields in the application template have no correspondingfields in the original resource data record, the following twoprocessing methods can be adopted.

In method 1, the field is ignored, and the value of the field in theapplication template is set as null. The value of the field can beallocated manually by the enterprise or manager through a self-serviceplatform.

In method 2, if some fields in the application template do not havedefinite corresponding fields in the original resource data record, butsome fields in the original resource data record may include theinformation required by the fields in the application template, thefields in the original resource data record that may include theinformation required by the fields in the application template arereferred to as ambiguous fields. FIG. 4 is a flow chart of a method forrecording a subscriber application template according to an embodimentof the present invention. The method includes the following blocks.

Block 400: A field is extracted from the application template.

Block 401: It is determined whether the field exists in the originalresource data record. If the field exists in the original resource datarecord, the process proceeds to Block 405; if the field does not existin the original resource data record, the process proceeds to Block 402.

Block 402: It is determined whether an ambiguous field exists in theoriginal resource data record. If the ambiguous field exists in theoriginal resource data record, the process proceeds to Block 403; if theambiguous field does not exist in the original resource data record, theprocess proceeds to Block 404.

Block 403: A key field is analyzed and extracted from the ambiguousfield, and a value of the key field is recorded in the applicationtemplate, and the process ends.

In this block, a current segmentation can be used to perform splitanalysis on the ambiguous field to extract effective key words. Thesplit analysis can be carried out in various ways, and theimplementation thereof is known to those skilled in the art, so thedetails will not be described herein again.

In this manner, a mapping table between some fields in the applicationtemplate and their corresponding ambiguous fields need to be preset inthe labeling module 100. Thereby, the ambiguous fields mapping to thefields extracted from the application template can be queried throughthe mapping table. Meanwhile, in this manner, the labeling module 100further has a split analysis function.

Block 404: The value of the field in the application template is set asnull, and the process ends.

Block 405: The value of the field is recorded in the applicationtemplate.

A mapping table is shown in Table 7 as an example for illustration:

TABLE 7 Fields in the application template Ambiguous fields BrandCompany profile Taste Company profile

It is assumed that a data in the original resource data record recordsthe registration information of an auto sales company. The registrationinformation includes the company's telephone number, name, industry,address, and profile with descriptions involving “BMW”. The parametersin the invoked auto sales application template include telephone number,company name, address, and brand, and the brand field has severalalternative values such as MAZDA, BMW, NISSAN, and VW. When thesubscriber information is labeled, values of the telephone number,company name, and address fields extracted from the original record arewritten into the corresponding fields in the auto sales applicationtemplate. As the brand field has no corresponding field in the originalresource data record, its ambiguous field obtained from the mappingtable in Table 7 is company profile. Split analysis is performed on thecompany profile field in the original resource data record, and “BMW” isset as a value of the brand field and written into the brand field ofthe auto sales application template.

Block 302: The application template after recording is stored.

Till now, the labeling of the subscriber information is finished, andthe subscriber is referred to as a specific subscriber.

Block 303: It is determined whether original resource database exists.If the original resource database exists, the process returns to Step300; otherwise, the process ends.

It can be seen from the description of the information labeling unit 10in FIG. 1 that, the labeled specific subscriber information is stored inthe specific subscriber labeling library 103.

Seen from the information labeling process in FIG. 3, a very importantstep is calling an application template to describe a specificsubscriber. The application template is designed based on an OntologyLanguage. After the original resource data is written into theapplication template, the labeling module 100 automatically generatesthe labeled information file of the specific subscriber informationdescribed by the original resource data, thus finishing the attributeinformation labeling of the specific subscriber. Information of two autosales companies before and after being labeled is given below forcomparison. Table 8 shows the information of auto sales companies beforebeing labeled.

TABLE 8 Enterprise Telephone name number District Address Class ServicesSHUMYIP 0755-26710686 Shenzhen, Building 9, Auto mainly running theTOYOTA Guangdong Maqueling sales auto sales of Automobile IndustrialTOYOTA , and also Sales & Zone providing auto Service Co., maintenanceLtd. services Feiyang 0755-82391435 Shenzhen, Building Auto mainlyrunning the Automobile Guangdong 38, sales auto sales of brands Sales &Maqueling such as CHERY , Service Co., Industrial and also providingLtd. Zone auto insurance services

In Table 8, the characters underlined and in boldface are key wordssplit from the ambiguous field “Services” in the original resource datarecord.

After being labeled, the original resource data information is writteninto the application template to form the labeled information in Table9:

TABLE 9  <specific subscriber 1>  < telephone number>0755-26710686</telephone number>  <template name>auto sales </template name> <attribute parameter>   <Group 1: basic attributes>    <enterprisename>SHUMYIP TOYOTA Automobile Sales & Service Co., Ltd. </enterprisename>    <district >Shenzhen, Guangdong</district >    <Address>Building9, Maqueling Industrial Zone</Address>    <Postcode></Postcode>   <Website></Website>   </Group 1: basic attributes>   <Group2: extended attributes>    <Brand>TOYOTA </Brand>    <service items>autosales, auto maintenance</service items>   </Group 2: extendedattributes>  </attribute parameter>  </specific subscriber 1>  <specificsubscriber 2>  < telephone number>0755-82391435</ telephone number> <template name>auto sales </template name>  <attribute parameter>  <Group 1: basic attributes>    <enterprise name>Feiyang AutomobileSales & Service Co., Ltd. </enterprise name>    <district>Shenzhen,Guangdong</district>    <Address>Building 38, Maqueling IndustrialZone</Address>    <Postcode></Postcode>    <Website></Website>   </Group1: basic attributes>   <Group 2: extended attributes>    <Brand>CHERY</Brand>    <service items>auto sales, auto insurance</service items>  </Group 2: extended attributes>  </attribute parameter>  </specificsubscriber 2>

In Table 9, the italic characters are labeled information.

Further, if the obtained communication record information does notinclude the fields described in the restrictions of the subscriberinformation transferring strategy, the method of the present inventionmay further preprocess the communication records, i.e., extract a presettarget field from the original communication record fields to form a newrecord and store the new record. The target field at least includes acommunication subject ID field identifying the owner of thecommunication records, a contact party ID field identifying thecommunication objects, and an additional field generated by processingthe communication record according to preset requirements.

The target field is set by a manager in a way varied with the format ofthe communication records. An example of preprocessing an original phonebill is shown below for illustrating a preprocessing method.

Assuming a phone bill of a subscriber 13526843612 for the first ten daysin June is shown in Table 10:

TABLE 10 Place Type of the Type Time Duration Mobile Toll Ser.Subscriber of the calling/called of the Counterpart's Date of the of theof the phone call No. number call party call number call call callcharge charge 1 13526843612 755 Calling party Local 13343857303 2006-6-117:13 00:12:23 / / 2 13526843612 755 Calling party Local 133438573032006-6-1 23:00 00:45:56 / / 3 13526843612 755 Called party Local13343857303 2006-6-1 19:00 00:09:48 / / 4 13526843612 755 Calling partyLocal 0755-26710686 2006-6-5 09:30 00:15:33 / / 5 13526843612 755Calling party Local 0755-26710686 2006-6-8 14:30 00:05:53 / / 613526843612 755 calling party Local 0755-82391435 2006-6-8 15:3000:03:53 / / 7 13526843612 755 Calling party Local 0755-823914352006-6-9 08:30 00:05:53 / / 8 13526843612 755 Called party Local13892983773 2006-6-9 10:30 00:02:26 / / 9 13526843612 755 Called partyLocal 13343857303 2006-6-10 12:00 00:09:12 / /

It is assumed that the preprocessing is performed on the format of theoriginal phone bill, and the set target fields include subscribernumber, serial number, and counterpart's number, i.e., a contact partyID field. The aforementioned processing on the communication recordsaccording to requirements is to consolidate the bill records under thesame counterpart's number, and the added additional fields include thenumber of calls and total call duration. The new records formed afterconsolidating are shown in Table 11:

TABLE 11 Subscriber Counterpart's Total call number Ser. No. numberNumber of calls duration 13526843612 1 13343857303 4 01:17:1913526843612 2 13892983773 1 00:02:26 13526843612 3 0755-26710686 200:21:26 13526843612 4 0755-82391435 2 00:09:46

Assuming that it is possible to obtain the distance of a call by somemeans, the call distance may well serve as a parameter to determine thedegree of relationship between the two parties in communication.

An example for illustrating the generation process of the subscriberinformation is shown below with reference to FIG. 1. FIG. 5 is a flowchart of an embodiment the present invention, including the followingblocks.

Block 500: It is determined whether subscriber communication recordsexist. If subscriber communication records exist, the process proceedsto Block 501; if subscriber communication records do not exist, theprocess ends.

Herein, it is assumed that the subscriber information generating module120 extracts a group of preprocessing bills from the new record library111, as shown in Table 12. The subscriber number is the communicationsubject ID field, and the counterpart's number is the contact party IDfield. Therefore, the determination result of this block is that thesubscriber communication records exist.

TABLE 12 Subscriber Counterpart's Total call number Ser. No. numberNumber of calls duration 13526843612 1 13343857303 4 01:17:1913526843612 2 13892983773 1 00:02:26 13526843612 3 0755-26710686 200:21:26 13526843612 4 0755-82391435 2 00:09:46

Blocks 501-503: A subscriber communication record is obtained, and acommunication subject ID is obtained from the record. It is determinedwhether the communication subject information mapping to thecommunication subject ID exists. If the communication subjectinformation exists, the process proceeds to Block 504; if thecommunication subject information does not exist, a subscriberinformation record of the communication subject is created.

In this step, it is assumed that a subscriber communication recordextracted by the subscriber information generating module 120 is asshown in Table 13.

TABLE 13 Subscriber Counterpart's The number of Total call number Ser.No. number calls duration 13526843612 1 13343857303 4 01:17:19

The subscriber information generating module 120 traverses thesubscriber information base 121, and determines whether the subscribernumber 13526843612 is recorded in the subscriber information base 121.If the subscriber number 13526843612 is not recorded in the subscriberinformation base 121, a subscriber information record file (as shown inTable 4) of the subscriber is created, i.e., generating a nullsubscriber description information record for the subscriber 13526843612in the subscriber information base.

Block 504: A contact party ID is obtained from the subscribercommunication record.

The subscriber information generating module 120 reads a contact partyID number of the communication record shown in Table 13, i.e., thecounterpart's number 13343857303.

Block 505: It is determined whether the labeled information of thecontact party exists. If the labeled information exists, the processproceeds to Step 507; if the labeled information does not exist, theprocess proceeds to Step 506.

In this block, it is assumed that the subscriber information generatingmodule 120 traverses the specific subscriber labeling library 103, andfinds out by query that the counterpart's number 13343857303 has notbeen labeled.

Block 506: An information transferring strategy of an unspecificsubscriber is invoked, and the process proceeds to Block 508.

In this block, it is assumed that the information transferring strategyof the unspecific subscriber called by the subscriber informationgenerating module 120 from the strategy pool 122 is: IP={(the number ofcalls>3)∩(total call duration>00:30:00)}.

Block 507: An information transferring strategy of a specific subscriberis invoked.

Block 508: It is determined whether the conditions are satisfied. If theconditions are satisfied, the process proceeds to Block 509; if theconditions are not satisfied, the process returns to Block 500.

In this block, according to the fields described in the informationtransferring strategy IP of the unspecific subscriber, the subscriberinformation generating module 120 reads the number of calls and totalcall duration in the subscriber communication record shown in Table 13in sequence, so as to determine whether the conditions set in IP aresatisfied.

Apparently, in this embodiment, seen from Table 13, the number of callsis four, and the total call duration is 01:17:19, both meeting theconditions set in IP that the number of calls>3 and the total callduration>00:30:00.

Block 509: The information of the contact party is recorded, and theprocess returns to Block 500.

The contact party 13343857303 is added into the subscriber descriptioninformation of 13526843612.

A contact weight of the contact party can be further generated andrecorded. It is assumed that the contact weight is a ratio of the numberof calls with the contact party in the total number of calls during aperiod of time. As shown in Table 12, in a period of four records, thecontact weight of the contact party 13343857303 is

$S = {\frac{4}{4 + 1 + 2 + 2} = {\frac{4}{9}.}}$

Through the above processes, the information of the unspecificsubscriber 13343857303 serves as the subscriber description informationof the communication subject 13526843621.

In the same way, a second record is extracted, and it is assumed thatthe queried counterpart's number 13892983773 in the second record is anunspecific subscriber. Seen from the process of FIG. 5, similarly, aninformation transferring strategy of an unspecific subscriber is called,and it can be found out that the number of calls in the second record isonce and the total call duration is 00:02:26, which do not meet theconditions set in IP, so this bill record should be ignored andabandoned.

A third record is extracted, and it is assumed that the queriedcounterpart's number 0755-26710686 in the third record is a specificsubscriber. The contact party 0755-26710686 belongs to the auto salesclass, and the labeled information of the contact party is shown inTable 9. Seen from the process of FIG. 5, in Step 507, the specificsubscriber labeling library 103 reads the application template name of0755-26710686 from the labeled information, and invokes an informationtransferring strategy of a specific subscriber mapping to theapplication template from the strategy pool 122. It is assumed that theinformation transferring strategy of the specific subscriber is: I={(thenumber of calls>1)}. Seen from the third record, the number of callsmade between the subscriber number 13526843612 and the counterpart'snumber 0755-26710686 are two, which meets the condition set in I, i.e.,the number of calls>1. Therefore, the information of the contact party0755-26710686 is added into the subscriber description information ofthe communication subject 13526843612. Herein, it should be noted that,besides adding the counterpart's number 0755-26710686 into thesubscriber description information of the communication subject13526843612, transferable parameters in the corresponding subscriberlabeled information of the counterpart's number 0755-26710686 is alsoadded.

Further, a contact weight of the contact party is generated andrecorded. It is assumed that the contact weight is a ratio of the numberof calls with the contact party in the total number of calls during aperiod of time. As shown in Table 12, in a period of four records, thecontact weight of the contact party 0755-26710686 is

$S = {\frac{2}{4 + 1 + 2 + 2} = {\frac{2}{9}.}}$

As the contact party 0755-26710686 is a labeled specific subscriber, amethod for recording the transferable parameters in the correspondingsubscriber labeled information of the counterpart's number 0755-26710686is adding corresponding preferential attributes in the subscriberdescription information. In particular, the method includes traversingthe preferential attributes of the communication subject subscriber, anddetermining whether the preferential attributes of the communicationsubject subscriber include attribute records of the auto sales class. Inthis embodiment, assuming that it is the first time for thecommunication subject subscriber to contact a specific subscriber of theauto sales class, the auto sales class records and correspondingtransferable parameters are directly added into the subscriberpreferential attributes. And in this embodiment, it is assumed that thetransferable parameters in the auto sales template are brand andservices.

A fourth record is extracted. It is assumed that the contact party0755-82391435 belongs to the auto sales class, and the labeledinformation of the contact party is shown in Table 9. The processingflow is identical to the third record and only varies in adding thepreferential attributes. As the preferential attribute records of theauto sales class already exist, when the record is processed, it needsto determine whether the transferable parameters in the labeledinformation of the contact party 0755-82391435 exist in the preferentialattribute records. If the transferable parameters exist in thepreferential attribute records, no operation will be performed, or thetransferable parameters in the labeled information of the contact party0755-82391435 are added to overwrite the original records; otherwise,the transferable parameters in the labeled information of the contactparty 0755-82391435 are added into the preferential attributes, so as toupdate the preferential attributes.

According to the process in FIG. 5, after the four records in Table 12are processed, the description information of the subscriber isgenerated as shown in Table 14:

TABLE 14  <subscriber 1>   <number>13526843612</number>  < socialrelationship attributes>    <unspecific subscriber>      <unspecificsubscriber 1>      <number>13343857303</number>       <contactweight>4/9</contact weight>      </unspecific subscriber 1>   </unspecific subscriber>    <specific subscriber>      <specificsubscriber 1>      <number>0755-26710686</number>       <name>SHUMYIPTOYOTA Automobile Sales & Service Co., Ltd. </name>      <contactweight>2/9</contact weight>      </specific subscriber 1>      <specificsubscriber 2>      <number>0755-82391435</number>       <name>FeiyangAutomobile Sales & Service Co., Ltd.</name>      <contactweight>2/9</contact weight>      </specific subscriber 2>    </specificsubscriber>  </ social relationship attributes>   <preferentialattribute>    <application template 1>    <template name>auto sales</template name>    <brand>TOYOTA, CHERY </Brand>     <serviceitems>auto sales, auto maintenance, auto insurance</service items>   </application template 1>   </preferential attribute>  </subscriber1>

The phone bill above is only taken as an embodiment for illustration.The scheme of the present invention is also applicable to communicationmodes like Email and IM, for example, labeling the enterprise Email andIM numbers. Moreover, the scheme of the present invention is alsoapplicable to data services process like ring back tone (RBT) download.For example, the present invention can be used for creating ontologydescription templates corresponding to various RBTs, labeling the RBTsprovided by service providers (SPs) as specific subscribers, andanalyzing the subscriber description information in service records ofthe subscriber data services.

Though illustration and description of the present disclosure have beengiven with reference to preferred embodiments thereof, it should beappreciated by persons of ordinary skill in the art that various changesin forms and details can be made without deviation from the spirit andscope of this disclosure, which are defined by the appended claims.

1. A system for generating communication subscriber descriptioninformation, comprising: an information labeling unit, adapted to labeloriginal information of a specific communication subscriber; and asubscriber information generating unit, adapted to generatecommunication subscriber description information; wherein theinformation labeling unit comprises a labeling module, an originalresource database, an application template ontology library, and aspecific subscriber labeling library; the original resource database isadapted to record the original information of a subscriber to belabeled; the application template ontology library is adapted to buildand store an application template describing a class and classattributes of the application for different applications; the labelingmodule is adapted to obtain the original information of the subscriberto be labeled from the original resource database, invoke an applicationtemplate corresponding to the class from the application templateontology library according to the class of the original information,fill information corresponding to the application template in theoriginal information into the application template so as to label theoriginal information, and store the labeled original information in thespecific subscriber labeling library; the subscriber informationgenerating unit comprises a subscriber information generating module, asubscriber information base, a strategy pool, and a strategy settingmodule; the subscriber information generating module is adapted toobtain communication record information externally, query the specificsubscriber labeling library, and add, according to an informationtransferring strategy of an subscriber in the strategy pool, qualifiedcontact party identification (ID) information and, when the subscriberis a specific subscriber, corresponding subscriber labeled informationof the qualified contact party ID information stored in the specificsubscriber labeling library into the communication subscriberdescription information of a communication subject and store thecommunication subscriber description information in the subscriberinformation base; the strategy setting module is adapted to set andstore various subscriber information transferring strategies into thestrategy pool; the strategy pool is adapted to store and provide varioussubscriber information transferring strategies for the subscriberinformation generating module; and the subscriber information base isadapted to store subscriber description information files of acommunication subject.
 2. The system according to claim 1, furthercomprising a preprocessing unit adapted to preprocess communicationrecords, and the preprocessing unit comprising a record preprocessingmodule and a new record library, wherein: the record preprocessingmodule is adapted to extract a preset target field from fields of theexternally obtained communication record information, generate anadditional field after processing the communication records according toa preset requirement, and store a new record composed of the targetfield and the additional field; and the new record library is adapted tostore and provide the new record composed of the target field and theadditional field to the subscriber information generating module.
 3. Thesystem according to claim 1, wherein the information labeling unitfurther comprises a self-service module adapted to provide asubscriber-oriented interface, so as to update labeling results in thespecific subscriber labeling library through the labeling module (100)by using the self-service module.
 4. The system according to claim 3,wherein the self-service module is one of an operating platform, aclient in a client/server (C/S) architecture, and a client in abrowser/server (B/S) architecture.
 5. The system according to claim 1,wherein the labeling module further comprises a mapping table betweenfields in the application template and their corresponding ambiguousfields; and the labeling module further comprises a split function foranalyzing the ambiguous fields corresponding to the fields in theapplication template so as to extract a key field.
 6. The systemaccording to claim 1, wherein the application template comprises anapplication template name and application template parameters describingthe class attributes of the class indicated by the application templatename; the application template name is identical to the name of theclass.
 7. The system according to claim 6, wherein the applicationtemplate further comprises association relationships between differentclasses.
 8. A method for generating communication subscriber descriptioninformation, comprising presetting a subscriber information transferringstrategy for determining whether or not to add contact party informationinto communication subscriber description information of a communicationsubject, the method further comprising: obtaining communication recordinformation, and determining whether the contact party identification(ID) information in the communication record information exists ingenerated subscriber labeled information, if the contact partyidentification (ID) information in the communication record informationexists in generated subscriber labeled information, recording, accordingto an information transferring strategy of a specific subscriber in thepreset subscriber information transferring strategy, the qualifiedcontact party information in the communication record information intocommunication subscriber description information of the communicationsubject.
 9. The method according to claim 8, wherein the contact partyinformation comprises the contact party identification (ID) information.10. The method according to claim 9 wherein the contact partyinformation further comprises subscriber labeled informationcorresponding to the contact party ID information.
 11. The methodaccording to claim 10, further comprising: if the contact partyidentification (ID) information in the communication record informationdose not exist in generated subscriber labeled information, recording,according to an information transferring strategy of an unspecificsubscriber in the preset subscriber information transferring strategy,the qualified contact party ID information in the communication recordinformation into the communication subscriber description information ofthe communication subject.
 12. The method according to claim 11, whereinan application template describing a class and class attributes of theapplication is respectively preset for different applications, and themethod for generating the subscriber labeled information comprises:extracting an original resource data record, and obtaining the classname of the class of the original resource data record; invoking,according to the obtained class name, an application templatecorresponding to the class name, and recording, according to fieldscontained in the invoked application template, a corresponding fieldvalue in the record into the application template; and storing theapplication template after recording.
 13. The method according to claim12, wherein if parts of the fields in the application template do notexist in the original resource data record, the method for recording thecorresponding field value in the original resource data record into theapplication template comprises setting the field value in theapplication template as null.
 14. The method according to claim 12,wherein if parts of the fields in the application template do not existin the original resource data record, the method for recording thecorresponding field value in the original resource data record into theapplication template comprises: presetting a mapping table between thefields in the application template and their corresponding ambiguousfields; and querying the mapping table to determine whether an ambiguousfield of the field in the application template exists in the originalresource data record, and if the ambiguous field of the field in theapplication template exists in the original resource data record,analyzing and extracting a key field from the ambiguous field, andrecording a value of the key field in the corresponding field of theapplication template; if the ambiguous field of the field in theapplication template does not exist in the original resource datarecord, setting the value of the field in the application template asnull.
 15. The method according to claim 14, wherein a method foranalyzing and extracting the key field is split analysis.
 16. The methodaccording to claim 11, wherein if a field described in conditions of thesubscriber information transferring strategy does not exist in theobtained communication record information, before determining whetherthe contact party ID information in the communication record informationexists in the generated subscriber labeled information, the methodfurther comprises: extracting a preset target field from fields of theobtained communication record, generating an additional field throughprocessing the communication record information according to a presetrequirement, and forming new communication record information.
 17. Themethod according to claim 11, wherein if the contact party IDinformation in the communication record information exists in thegenerated subscriber labeled information, the recording the qualifiedcontact party information in the communication record information intocommunication subscriber description information comprises: traversingpreset preferential attributes in the subscriber description informationof the communication subject subscriber to determine whether a class ofthe subscriber labeled information exists in the preferentialattributes; if the class of the subscriber labeled information does notexist in the preferential attributes, adding the class of the subscriberlabeled information and transferable parameters therein into thepreferential attributes of the communication subject subscriber; and ifthe class of the subscriber labeled information exists in thepreferential attributes, determining whether the transferable parametersin the subscriber labeled information exist in the preferentialattributes, and adding the transferable parameters in the subscriberlabeled information into the preferential attributes if the transferableparameters in the subscriber labeled information do not exist in thepreferential attributes.
 18. The method according to claim 11, furthercomprising: building, in the communication subscriber descriptioninformation, contact frequency or intimacy between the communicationsubject and an unspecific subscriber or a specific subscriber accordingto a preset composite operation relationship of a designated field. 19.The method according to claim 12, wherein the application template iscreated on the basis of an Ontology Language.
 20. The method accordingto claim 19, wherein the application template comprises an applicationtemplate name and application template parameters describing relatedclass attributes of the class indicated by the application templatename.